Configure standard and ts-standard as linter and formatter for JS and TS #918
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bigmontz
force-pushed
the
5.0-auto-format
branch
2 times, most recently
from
3e63af1 to
4fcc693
Compare
bigmontz
force-pushed
the
5.0-auto-format
branch
from
4fcc693 to
86ffce1
Compare
bigmontz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The linter and formatter configuration in the pre-commit hook helps with standardisation of the code and avoiding programming errors.
Moving the configuration to use
standardandts-standardinstead ofeslintavoids manage different libraries and plugins. Thus it enables an easier project maintenance.